home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
w3euti22.zip
/
UTI.HIS
< prev
next >
Wrap
Text File
|
1992-08-06
|
6KB
|
134 lines
Enhanced UTIs for WildCat 3.0 & 3.5
Changes -- Minor Revision 2.2
6 August 1992
1. UTIRFLAG was not finding the correct user name keys to clear
mail-waiting flags. Corrected.
2. UTILSTRD now supports manual conference overrides, such as when
using WC Pro.
3. UTIIMPRT ensures that AUTONODE default is off at start of program.
Changes -- Revision 2.1
9 JULY 1992
1. Error log message cleaned up -- easier to read.
2. Modified error log control structure.
3. If there is an error updating NODEINFO.DAT, a message will be
logged, but the program will not halt. The master message
counters are kept in NODEINFO.DAT.
4. Added new routine that allows both implicit and explicit paths
in MAKEWILD. ie: both 'C:\WC30\DATA\' and 'C:DATA\' are
allowed.
5. The message thread key is now handled properly when subject
lines are greater then 25 characters -- only important when
crossing FidoNet messages with other networks.
6. UTILSTRD has been modified to:
A. Use only the CONFDESC.DAT in the MakeWild directory.
B. Report 'unsubscribed' conferences correctly.
C. Update 'unsubscribed' conferences correctly.
7. When exporting messages, ASCII (255) is converted to ASCII (0).
This will avoid situations where PC Relay sometimes gets confused.
8. Autonode selection was corrected.
9. Some routines were rewritten in Assembler.
Changes -- Revision 2.0
17 JUNE 1992
1. The UTIs automatically detect either the 3.0 or 3.5 record
formats. Depending on the version, there are different
routines for adding and deleting keys, and creating a new
message database.
2. Locked database delays now match the online user delays,
limiting the number/length of online delays. The mail import
event will now pause longer when a lock is encountered (1/2 to
1 second) but offline delays are preferable to online delays.
3. Automatic node ID selection is supported when the autonode
option is enabled in MAKEWILD. If WCNODEID is specified in
the DOS environment, the WCNODEID value will be used in place
of an autonode selection. If the WCNODEID value is currently
in use by another workstation (according to the AUTONODE.DAT
file), then the program will halt with an error.
4. If there are two or more blank spaces between an addressee's
first and last names (etc.) then the extra spaces will be
removed. This allows the "mail waiting" flag to be set
properly for a user.
5. If there is any error opening a message database, a message
will be sent to the error log, but PC Relay will continue to
function.
Changes -- Revision 1.2
12 MAY 1992
1. After 8 near non-stop days of studying user comments, testing
and trouble-shooting, the v1.1 UTIs were ready for release.
The memory requirements were accurately calculated and
everything worked fine. After the final testing, the programs
were recompiled with a minor logo change and released. 12
hours later, v1.1 was recalled; when the programs were
recompiled, a change affected both utiEXPRT and utiLSTRD
causing them to fail for insufficient memory.
Version 1.2 fixes this oversight.
Changes -- Revision 1.1
11 MAY 1992
Memory: To run PC Relay 4.10/4.11 with the UTIs, you will need at
least 400K of memory. If the UTIs do not have enough
memory, they will stop with an error message and halt the
PC Relay event. The error message will indicate how much
additional memory is needed.
By providing up to 75K more memory to the UTIs, you may
see some added speed improvement.
Errors: Some "hard" errors in UTI v1.0 have been changed to
"soft" errors. Soft errors do not halt the entire PC
Relay event; they cause the current message conference to
be skipped and a reminder is written to the UTI.LOG for
later correction. Some of these errors are:
1. Unable to lock the database.
2. Message conference is not defined.
3. Error in the conference database.
4. Unable to open/create a conference database.
Locks: The UTIs have been fine-tuned so that fewer file lock
errors are encountered. They can now pass this import
stress test:
==> 3 nodes, each adding and deleting 1000 messages to
the same conference at the same time. No file
locks are encountered.
Other Errors
1. There was a file handle problem when running the UTIs in
DESQview, with SHARE.EXE loaded and in WildCat's Single-line
mode. This has been corrected.
2. There was a problem (mainly confusion) when two or more nodes
tried to create a conference database at the same time, or
when the UTIs were run in two windows at the same time. This
was mistaken for a disk cache/delayed writing error, but
turned out to be a problem with the conference status record.
3. Disk Caches -- Since correcting error #2 above, I no longer
have problems with delayed disk writes. My earlier warning
against them is withdrawn.
Questions or comments should be directed to Jim Metzler in the:
-- MSInet WildCat Support conference
-- RIME WildCat conference
-- WildNet 3rd Party Support conference
-- MSI HQ conferences
-- FidoNet WildCat conference
or at (508) 754-6512 (BBS)
(508) 799-7540 (voice)